Subject: RE: NTT Stex
Date: Sun, 4 Jul 1999 20:18:36 -0500
From: "Iseki, Nobuo" <Nobuo.Iseki@mts.com>
To: "Langseth, Jim" <Jim.Langseth@mts.com>, "Larson, Rod"
     <Rod.Larson@mts.com>, "Otsuka, Yutaka" <Yutaka.Otsuka@mts.com>

Hello ,
The customer informed me that the problem was fixed by making more space
in the STEX disk.
According to them , stexresponce.bin from 469D has been backup in STEX
computer and it filled up the disk.
Thank you for your help.
Nobuo Iseki

                -----Original Message-----
                From:   Langseth, Jim
                Sent:   Thursday, July 01, 1999 1:23 AM
                To:     Iseki, Nobuo
                Subject:        RE: NTT Stex

                Nobuo-san,

                NTT STEX works in a special way with the Digital 496D.
The achieved file is automatically sampled
                by the 469 during the test and put into a file that STEX
reads after the test is over.  The file is a binary file:

                C:\nttproj\stexresponse.bin         IMPORTANT - IT IS
LOCATED ON THE 469D COMPUTER

                STEX retrieves the file after the test over the network
from the 469D.  The file is checked to make sure the correct number of
points is included.

                I recommend that immediately after the error message,
the customer import the binary file ($B!D(J\stexresponse.bin) and check the
length of the time histories.  It should match exactly the number of
points in the drive time histories.

                Since this has always worked before, I wonder.  Has the
469D software changed recently?

                Best Regards,
                Jim
